src/main/kotlin/com/github/pyvenvmanage/actions/ConfigurePythonActionAbstract.kt:39

• actionPerformed is now restricted to directories, but it can still run on a non-venv directory (e.g. via keyboard shortcut) and then apply to whatever nested interpreter PythonSdkUtil.getPythonExecutable finds. If the action is meant to apply only when the selected directory itself is a venv, validate that here too (e.g. require pyvenv.cfg in the selected directory) so update() and actionPerformed() enforce the same target rule.

        val selectedPath = e.getData(CommonDataKeys.VIRTUAL_FILE)?.takeIf { it.isDirectory } ?: return

src/main/kotlin/com/github/pyvenvmanage/actions/ConfigurePythonActionAbstract.kt:30

• PythonSdkUtil.getPythonExecutable(dir.path) can still return an interpreter located in a child venv (as described in the PR body). With the current logic, right-clicking a non-venv directory that merely contains a venv could still enable this action, contradicting the stated behavior (only show on directories that are themselves a venv). Consider verifying that the detected interpreter belongs to the selected directory itself (i.e., the resolved venv root matches the selected directory).

        // Only offer the action on a directory that is itself a virtual environment. Resolving a file
        // to its parent made it appear on ordinary files (e.g. main.py) whose folder merely contains
        // a venv, which is not a valid interpreter target.
        val venvDir = e.getData(CommonDataKeys.VIRTUAL_FILE)?.takeIf { it.isDirectory }
        val pythonExecutable = venvDir?.let { PythonSdkUtil.getPythonExecutable(it.path) }

src/main/kotlin/com/github/pyvenvmanage/actions/ConfigurePythonActionAbstract.kt:43

• actionPerformed now ignores non-directory selections, but it still trusts PythonSdkUtil.getPythonExecutable(selectedPath.path) without checking that the returned interpreter belongs to selectedPath itself. If getPythonExecutable resolves an interpreter inside a child venv, this can still apply the action when the user right-clicks a non-venv directory that merely contains a venv.

        val selectedPath = e.getData(CommonDataKeys.VIRTUAL_FILE)?.takeIf { it.isDirectory } ?: return

        val pythonExecutable = PythonSdkUtil.getPythonExecutable(selectedPath.path)
        if (pythonExecutable == null) {

src/main/kotlin/com/github/pyvenvmanage/actions/ConfigurePythonActionAbstract.kt:42

• actionPerformed currently accepts any selected directory (even non-venv directories) and will attempt to configure an SDK if PythonSdkUtil.getPythonExecutable resolves (e.g. project root with a configured interpreter). This contradicts the updated update() logic and the PR description that the action should apply only to directories that are actual virtual environments. Consider applying the same VenvUtils.getPyVenvCfg gate here to keep behavior consistent and avoid configuring a non-venv directory as an interpreter target.

    override fun actionPerformed(e: AnActionEvent) {
        val project = e.project ?: return
        val selectedPath = e.getData(CommonDataKeys.VIRTUAL_FILE)?.takeIf { it.isDirectory } ?: return

src/test/kotlin/com/github/pyvenvmanage/actions/ConfigurePythonActionAbstractTest.kt:120

• This test name says it covers a non-directory selection, but the setup doesn’t explicitly make the selection non-directory, and it stubs VenvUtils.getPyVenvCfg directly (so the non-directory behavior isn’t really exercised). To make the intent and coverage clearer, either set virtualFile.isDirectory = false and rename the test to reflect what it asserts (no probing via PythonSdkUtil.getPythonExecutable when the selection is not a venv).

        @Test
        fun `disables action for non-directory selection`() {
            every { event.getData(CommonDataKeys.VIRTUAL_FILE) } returns virtualFile
            every { VenvUtils.getPyVenvCfg(virtualFile) } returns null